Repository navigation
Disable x32 image repositories without config-manager - #238
Merged
Merged
Conversation
Not every AlmaLinux i386 image ships the dnf config-manager plugin, and it can't be installed at that point because the image repositories are the ones being replaced. Set enabled=0 in the repository files instead. The files are %config(noreplace), so an almalinux-release update during provisioning doesn't re-enable them. Resolves: AlmaLinux/build-system#565
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves AlmaLinux/build-system#565
Follow-up to #237.
Summary
On prod the new "Disable image repositories in AlmaLinux x32 docker container" step fails:
Not every AlmaLinux i386 image ships the config-manager plugin (
python3-dnf-plugins-core), and it can't be installed at that point, because the image repositories are the ones being replaced.Changes
resources/roles/preparation/tasks/rhel.yml: setenabled=0in/etc/yum.repos.d/*.repowithsedinstead ofdnf config-manager --set-disabled '*'. Every section in the image repository files has an explicitenabled=line. The files are%config(noreplace), so analmalinux-releaseupdate during provisioning keeps the edited files and doesn't re-enable them.Testing
linux/386container withpython3-dnf-plugins-coreremoved (dnf config-managerfails as on prod) andvault.almalinux.orgresolving to 127.0.0.1: provision passes, and only the task repositories and EPEL are enabled afterwards.